Server node selection method and terminal device

ABSTRACT

Methods and terminal devices, including computer programs encoded on computer storage media, for selecting a server node. According to one of the methods, a terminal device first sends a connection request to one server node, and then sends a connection request to another server node after a time interval T. The terminal device first sends a connection request to a first server node. If the terminal device receives, within a first preset duration T, response information fed back by the first server node, the terminal device does not need to send a connection request to another server node. This helps save resources. In addition, the terminal device may establish a connection to a server node corresponding to received response information, and does not need to wait for feedback from another server node. This helps reduce a delay in establishing a connection between the terminal device and a server node.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is the U.S. national phase of International ApplicationNo. PCT/CN2018/102804 filed 28 Aug. 2018, which designated the U.S., theentire contents of which is hereby incorporated by reference.

TECHNICAL FIELD

Example embodiments relate to the field of terminal technologies, and inparticular, to a server node selection method and a terminal device.

BACKGROUND

With rapid development of terminal technologies, currently, anincreasing quantity of terminal devices can implement a network accessfunction. Actually, a network access process of a terminal device is aprocess of information exchange between the terminal device and aninternet content provider (ICP).

Currently, a process in which the terminal device accesses the ICP is asfollows: A user enters a website in the terminal device, and the websiteincludes a domain name. The terminal device sends the domain name to adomain name server (DNS). After receiving the domain name, the DNSserver determines a plurality of IP addresses corresponding to thedomain name, and sends information about the plurality of IP addressesto the terminal device. Each of the plurality of IP addressescorresponds to one server node. Therefore, the terminal device needs toselect one server node from the plurality of server nodes, and thenaccesses the ICP by using the one server node.

However, the user imposes an increasingly high requirement on a networkaccess speed of the terminal device. Therefore, how to select a servernode with comparatively good network quality from a plurality of servernodes is a problem to be resolved.

FIG. 1 is a schematic diagram of a process in which a client selects oneserver node from a plurality of server nodes in the prior art. As shownin FIG. 1, the client sends a domain name to a DNS server. Afterreceiving the domain name, the DNS server determines, based on thedomain name, one or more IP addresses corresponding to the domain name,and generates an IP address list. For example, the IP address listincludes two IP addresses: an IP 1 and an IP 2. The IP 1 corresponds toa server node 1, and the IP 2 corresponds to a server node 2.

Still referring to FIG. 1, an example in which a preset duration that isset by the client is 30 s is used. After receiving the IP address list,the client sends a first connection request to the server node 1 at00:50 s. If the client does not receive, within is (in other words,before 01:50 s), response information fed back by the server node 1, theclient continues to send a second connection request to the server node1 at 01:50 s. If the client still does not receive, within 2 s (in otherwords, before 03:50 s), the response information fed back by the servernode 1, the client continues to send a third connection request to theserver node 1 at 03:50 s. If the client still does not receive, within 4s (in other words, before 07:50 s), the response information fed back bythe server node 1, the client continues to send a fourth connectionrequest to the server node 1 at 07:50 s. If the client still does notreceive, within 8 s (in other words, before 15:50 s), the responseinformation fed back by the server node 1, the client continues to senda fifth connection request to the server node 1 at 15:50 s. If theclient still does not receive, within 16 s (in other words, before 31:50s), the response information fed back by the server node 1, the clienttheoretically needs to continue to send a sixth connection request tothe server node 1 at 31:50 s. However, 31:50 s minus 00:50 s equals 31s, which exceeds the preset duration 30 s. Therefore, the client sendsthe first connection request to the server node 2 at 30:50 s (00:50 s+30s), instead of sending the sixth connection request to the server node 1at 31:50 s (in FIG. 1, that the client sends the sixth connectionrequest to the server node 1 at 31:50 s is indicated by using a dashedline, in other words, the client does not send the sixth connectionrequest to the server node 1 at 31:50 s).

It can be learned that, in the prior art shown in FIG. 1, after the DNSserver returns the IP address list to the client, the client firstattempts to establish a connection to a server node corresponding to anIP address in the IP address list. When the server node does not respondfor a long time, the client does not automatically retry a server nodecorresponding to another IP address in the IP address list, but triesanother server node after duration in which the client attempts toestablish the connection to the server node expires. This manner likelydecreases the network access speed of the terminal device anddeteriorates user experience.

SUMMARY

Example embodiments provide a server node selection method and aterminal device, to select a server node with comparatively good networkquality from a plurality of server nodes.

According to a first aspect, an embodiment of this application providesa server node selection method, and the method is applied to a terminaldevice. The method includes: sending, by the terminal device, a domainname resolution request to a DNS server, where the domain nameresolution request carries a domain name, and the domain name resolutionrequest is used to request an IP address corresponding to the domainname; receiving, by the terminal device, N IP addresses fed back by theDNS server, where each of the N IP addresses corresponds to one servernode, and N is greater than or equal to 2; sending, by the terminaldevice, a connection request to one server node in the N server nodes ata first moment; if the terminal device receives, before a second moment,response information fed back by the one server node, establishing, bythe terminal device, a connection to the one server node; or if theterminal device does not receive, before a second moment, responseinformation fed back by the one server node, sending, by the terminaldevice, a connection request to another server node in the N servernodes at the second moment; receiving, by the terminal device, firstresponse information at a moment between the second moment and a thirdmoment; and establishing, by the terminal device, a connection to aserver node that sends the first response information, where the servernode that sends the first response information is the one server node orthe another server node.

In this embodiment of this application, the terminal device sends aconnection request to a server node at a specific time interval (theterminal device first sends a connection request to one server node, andthen sends a connection request to another server node after a timeinterval T), so that a sudden increase of concurrent visits can beavoided. The terminal device first sends a connection request to a firstserver node. If the terminal device receives, within a first presetduration T, response information fed back by the first server node, theterminal device does not need to send a connection request to anotherserver node. This helps save resources. In addition, the terminal devicemay establish the connection to the server node corresponding to thereceived first response information, and does not need to wait for afeedback from another server node. This helps reduce a delay ofestablishing a connection between the terminal device and a server node.

In a possible implementation, when receiving second responseinformation, the terminal device discards or skips responding to thesecond response information, where a server node that sends the secondresponse information is the one server node or the another server node,and is different from the server node that sends the first responseinformation.

For example, if the first response information received by the terminaldevice is sent by a server node 1, the terminal device establishes aconnection to the server node 1. If the terminal device subsequentlyreceives response information of a server node 2, the terminal devicemay not process or may discard the response information of the server 2.This manner helps improve processing efficiency of the terminal deviceand save an unnecessary calculation amount.

In a possible implementation, if the first response information is sentby the one server node, before the establishing, by the terminal device,a connection to a server node that sends the first response information,the terminal device waits for a first preset duration starting from afourth moment at which the terminal device receives the first responseinformation, to determine that the terminal device does not receive,within the first preset duration, response information sent by theanother server node, where the first preset duration is less than a timedifference between the fourth moment and the third moment.

In this embodiment of this application, an example in which the oneserver node is the server node 1 and the another server node is theserver node 2 is used. The terminal device first sends a connectionrequest to the server node 1, and then sends a connection request to theserver node 2. After the terminal device sends the connection request tothe server node 2, assuming that the first response information receivedby the terminal device is sent by the server node 1, the terminal devicemay wait for a period of time after receiving the first responseinformation. If the terminal device receives, within this period oftime, response information fed back by the server node 2, it indicatesthat the server node 2 responds comparatively quickly, and therefore theterminal device establishes a connection to the server node 2.Alternatively, if the terminal device does not receive, within thisperiod of time, response information fed back by the server node 2, theterminal device establishes a connection to the server node 1. In thismanner, the terminal device can flexibly select to establish theconnection to the server node 1 or establish the connection to theserver node 2.

In a possible implementation, a time difference between the first momentand the second moment is a first duration T, and a time differencebetween the second moment and the third moment is the first duration T.

In this embodiment of this application, the time difference between thefirst moment and the second moment and the time difference between thesecond moment and the third moment are the same T. Certainly, the timedifference between the second moment and the third moment and the timedifference between the second moment and the third moment mayalternatively be different. This is not limited in the embodiments ofthe present disclosure.

In a possible implementation, the terminal device sends a networkresource request to the server node that sends the first responseinformation, where the network resource request is used to request anetwork resource; and if the terminal device does not receive, withinsecond preset duration, the network resource fed back by the server nodethat sends the first response information, the terminal device sends anetwork resource request to the server node that sends the secondresponse information.

In this embodiment of this application, after the terminal deviceestablishes the connection to the server node that sends the firstresponse information, the terminal device requests the network resourcefrom the server node. If the terminal device does not receive, for along time, the network resource fed back by the server node that sendsthe first response information, the terminal device requests the networkresource from the server node that sends the second responseinformation. This manner helps reduce a delay of requesting a networkresource by the terminal device.

In a possible implementation, if the terminal device does not receive,before the third moment, the response information sent by the one servernode or the another server node, the terminal device sends a connectionrequest to a third server node in the N server nodes at the thirdmoment; and when the terminal device receives the first responseinformation at a moment between the third moment and a fifth moment, theterminal device establishes a connection to a server node that sends thefirst response information, where the server node that sends the firstresponse information is the one server node, the another server node, orthe third server node.

In this embodiment of this application, the terminal device sends aconnection request to a server node at a specific time interval. Thishelps save resources. In addition, if the terminal device sendsconnection requests to a plurality of server nodes at a specific timeinterval, the terminal device may establish the connection to the servernode corresponding to the received first response information, and doesnot need to wait for a feedback from another server node. This helpsreduce a delay.

In a possible implementation, a time difference between the third momentand the fifth moment is the first duration T.

In this embodiment of this application, the time difference between thefirst moment and the second moment, the time difference between thesecond moment and the third moment, and the time difference between thethird moment and the fifth moment may be the same T. Certainly, the timedifference between the second moment and the third moment, the timedifference between the second moment and the third moment, and the timedifference between the third moment and the fifth moment mayalternatively be different. This is not limited in the embodiments ofthe present disclosure.

According to a second aspect, an embodiment of this application providesa server node selection method, and the method is applied to a terminaldevice. The method includes: sending, by the terminal device, a domainname resolution request to a DNS server, where the domain nameresolution request carries a domain name, and the domain name resolutionrequest is used to request an IP address corresponding to the domainname; receiving, by the terminal device, N IP addresses fed back by theDNS server, where each of the N IP addresses corresponds to one servernode, and N is greater than or equal to 2; sending, by the terminaldevice, a connection request to one server node in the N server nodes ata first moment; if the terminal device receives, before a second moment,response information fed back by the one server node, establishing, bythe terminal device, a connection to the one server node; or if theterminal device does not receive, before a second moment, responseinformation fed back by the one server node, sending, by the terminaldevice, a connection request to another server node in the N servernodes at the second moment; receiving, by the terminal device at afourth moment between the second moment and a third moment, the responseinformation fed back by the one server node; waiting for, by theterminal device, a first preset duration starting from the fourthmoment, where the first preset duration is less than a time differencebetween the fourth moment and the third moment; and if the terminaldevice receives, within the first preset duration, response informationfed back by the another server node, establishing, by the terminaldevice, a connection to the another server node.

In this embodiment of this application, an example in which the oneserver node is a server node 1 and the another server node is a servernode 2 is used. The terminal device sends a connection request to aserver node at a specific time interval (the terminal device first sendsa connection request to the server node 1, and then sends a connectionrequest to the server node 2 after a time interval T). For example, theterminal device first sends the connection request to the server node 1.If the terminal device receives, within the first preset duration T,response information fed back by the server node 1, the terminal devicedoes not need to send a connection request to another server node. Thishelps save resources. In addition, after the terminal device sends theconnection request to the server node 2, assuming that the terminaldevice first receives the response information fed back by the servernode 1, the terminal device may wait for a period of time. If theterminal device receives, within this period of time, responseinformation fed back by the server node 2, it indicates that the servernode 2 responds comparatively quickly, and therefore the terminal devicecan establish a connection to the server node 2. In this manner, theterminal device can select, from the server node 1 and the server node2, a server node that responds comparatively quickly, to establish aconnection. This helps reduce a delay.

In a possible implementation, a time difference between the first momentand the second moment is a first duration T, and a time differencebetween the second moment and the third moment is the first duration T.

In a possible implementation, the terminal device sends a networkresource request to the another server node, where the network resourcerequest is used to request a network resource; and if the terminaldevice does not receive, within second preset duration, the networkresource fed back by the another server node, the terminal device sendsa network resource request to the one server node.

According to a third aspect, an embodiment of this application providesa server node selection method, and the method is applied to a terminaldevice. The method includes: sending, by the terminal device, a domainname resolution request to a DNS server, where the domain nameresolution request carries a domain name, and the domain name resolutionrequest is used to request an IP address corresponding to the domainname; receiving, by the terminal device, N IP addresses fed back by theDNS server, where each of the N IP addresses corresponds to one servernode, and N is greater than or equal to 2; sending, by the terminaldevice, a connection request to one server node in the N server nodes ata first moment; and if the terminal device receives, before a secondmoment, response information fed back by the one server node,establishing, by the terminal device, a connection to the one servernode; or if the terminal device does not receive, before a secondmoment, response information fed back by the one server node, sending,by the terminal device, a connection request to another server node inthe N server nodes at the second moment.

If the terminal device simultaneously receives two pieces of responseinformation fed back by the one server node and the another server node,the terminal device establishes a connection to a server nodecorresponding to first response information in the two pieces ofresponse information.

In this embodiment of this application, an example in which the oneserver node is a server node 1 and the another server node is a servernode 2 is used. The terminal device sends a connection request to aserver node at a specific time interval (the terminal device first sendsa connection request to the server node 1, and then sends a connectionrequest to the server node 2 after a time interval T). For example, theterminal device first sends the connection request to the server node 1.If the terminal device receives, within a first preset duration T,response information fed back by the server node 1, the terminal devicedoes not need to send a connection request to another server node. Thishelps save resources. In addition, after the terminal device sends theconnection request to the server node 2, the terminal devicesimultaneously receives the response information fed back by the servernode 1 and response information fed back by the server node 2, and it isconsidered that network quality of the two server nodes is acceptable.Therefore, the terminal device only needs to establish the connection tothe server node corresponding to the first response information in thetwo pieces of response information. This manner helps reduce a delay ofestablishing a connection between the terminal device and a server node.

In a possible implementation, the establishing, by the terminal device,a connection to a server node corresponding to first responseinformation in the two pieces of response information includes: if theterminal device first processes the first response information in thetwo pieces of response information, establishing, by the terminaldevice, the connection to the server node that sends the first responseinformation.

In this embodiment of this application, when the terminal devicesimultaneously receives the response information fed back by the servernode 1 and the response information fed back by the server node 2, theterminal device establishes a connection to a server node correspondingto response information that is processed first. This manner helpsreduce a delay of establishing a connection between the terminal deviceand a server node.

In a possible implementation, the establishing, by the terminal device,a connection to a server node corresponding to first responseinformation in the two pieces of response information includes:determining, by the terminal device, that a response time of the servernode that sends the first response information is less than a responsetime of a server node that sends the second response information; andestablishing, by the terminal device, the connection to the server nodethat sends the first response information.

In this embodiment of this application, when the terminal devicesimultaneously receives response information fed back by two servernodes, the terminal device establishes a connection to a server nodethat responds comparatively quickly. This manner helps reduce a delay ofestablishing a connection between the terminal device and a server node.

In a possible implementation, the terminal device sends a networkresource request to the server node that sends the first responseinformation, where the network resource request is used to request anetwork resource; and if the terminal device does not receive, withinsecond preset duration, the network resource fed back by the server nodethat sends the first response information, the terminal device sends anetwork resource request to the server node that sends the secondresponse information.

According to a fourth aspect, an embodiment of this application providesa terminal device, including a processor and a memory. The memory isconfigured to store one or more computer programs. When the one or morecomputer programs stored in the memory are executed by the processor,the terminal device is enabled to implement the method in the firstaspect or any possible implementation of the first aspect.Alternatively, when the one or more computer programs stored in thememory are executed by the processor, the terminal device is enabled toimplement the method in the second aspect or any possible implementationof the second aspect. Alternatively, when the one or more computerprograms stored in the memory are executed by the processor, theterminal device is enabled to implement the method in the third aspector any possible implementation of the third aspect.

According to a fifth aspect, an embodiment of this application furtherprovides a terminal device. The terminal device includes modules/unitsfor performing the method in the first aspect or any possibleimplementation of the first aspect; or the terminal device includesmodules/units for performing the method in the second aspect or anypossible implementation of the second aspect; or the terminal deviceincludes modules/units for performing the method in the third aspect orany possible implementation of the third aspect. These modules/units maybe implemented by hardware, or may be implemented by hardware executingcorresponding software.

According to a sixth aspect, an embodiment of this application furtherprovides a computer-readable storage medium. The computer-readablestorage medium includes a computer program. When the computer program isrun on a terminal device, the terminal device is enabled to perform themethod in the first aspect or any possible implementation of the firstaspect. Alternatively, when the computer program is run on a terminaldevice, the terminal device is enabled to perform the method in thesecond aspect or any possible implementation of the second aspect.Alternatively, when the computer program is run on a terminal device,the terminal device is enabled to perform the method in the third aspector any possible implementation of the third aspect.

According to a seventh aspect, an embodiment of this application furtherprovides a computer program product. When the computer program productis run on a terminal device, the terminal device is enabled to performthe method in the first aspect or any possible implementation of thefirst aspect. Alternatively, when the computer program product is run ona terminal device, the terminal device is enabled to perform the methodin the second aspect or any possible implementation of the secondaspect. Alternatively, when the computer program product is run on aterminal device, the terminal device is enabled to perform the method inthe third aspect or any possible implementation of the third aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a server node selection process in theprior art;

FIG. 2 is a schematic diagram of an application scenario according to anexample embodiment;

FIG. 3 is a schematic diagram of a hardware structure of a mobile phoneaccording to an example embodiment;

FIG. 4 is a schematic diagram of a software structure of a mobile phoneaccording to an example embodiment;

FIG. 5 is a schematic flowchart of a server node selection methodaccording to an example embodiment;

FIG. 6 is a schematic flowchart of a server node selection methodaccording to an example embodiment;

FIG. 7 is a schematic flowchart of a server node selection methodaccording to an example embodiment;

FIG. 8 is a schematic flowchart of a server node selection methodaccording to an example embodiment;

FIG. 9 is a schematic flowchart of a server node selection methodaccording to an example embodiment;

FIG. 10 is a schematic diagram of a process of a three-way handshakebetween a client and a first server node according to an exampleembodiment;

FIG. 11 is a schematic structural diagram of a terminal device accordingto an example embodiment;

FIG. 12 is a schematic structural diagram of another terminal deviceaccording to an example embodiment; and

FIG. 13 is a schematic structural diagram of another terminal deviceaccording to an example embodiment.

DESCRIPTION OF EMBODIMENTS

The following describes the technical solutions in the embodiments ofthis application with reference to the accompanying drawings in theembodiments of this application.

The following describes some terms in this application, to facilitateunderstanding of a person skilled in the art.

A client in the embodiments of this application may be a software orhardware module that requests a network resource. For example, if aterminal device is a mobile phone, the client may be an application (appfor short) in the mobile phone, such as Baidu or Sohu. Baidu is used asan example. Baidu may be used to request a network resource such as avideo, a picture, or a text.

A DNS query request device in the embodiments of this application may bea software or hardware module that sends a domain name resolutionrequest to a DNS server. The domain name resolution request includes adomain name, and the domain name resolution request is used to requestthe DNS to determine an IP address corresponding to the domain name. Forexample, if the terminal device is a mobile phone, the DNS query requestdevice may be a software or hardware module in the mobile phone.

It should be noted that an example in which the DNS query request deviceis a software module in a mobile phone is used. The software module maybe integrated into the foregoing client, in other words, an app, or maybe integrated into an operating system (for example, Android) in themobile phone. If the DNS query request device is integrated into theoperating system in the mobile phone, such as the Android operatingsystem, the DNS query request device may be Okhttp in the mobile phone.An example in which the DNS query request device is Okhttp in the mobilephone is used for description below.

An application in the embodiments of this application is a computerprogram that completes one or more specific operations. A mobile phoneis used as an example. When running an application, the mobile phone maydisplay a display interface of the application, so that man-machineinteraction can be implemented in the display interface. Usually, oneapplication can implement a specific function. For example, applicationsinclude Baidu, Sohu, various mailbox applications, WeChat, Tencent chatsoftware (QQ), WhatsApp Messenger, Line, a photo sharing application(instagram), Kakao Talk, and DingTalk.

The DNS server in the embodiments of this application stores acorrespondence between a domain name and an IP address, and isconfigured to query, based on a domain name, an IP address correspondingto the domain name. The DNS server may alternatively have another name,for example, a domain name system, a domain name resolution server, or adomain name resolution system. In other words, a name of the DNS serveris not limited in the embodiments of the present disclosure.

A uniform resource locator (URL) in the embodiments of this applicationmay be used to request a network resource. Generally, the URL includes adomain name. For example, if the URL is www.baidu.com/?fr=mhd_card, thedomain name is baidu.com; or if the URL is www.sina.com, the domain nameis sina.com.

For a server node in the embodiments of this application, an ICP mayusually deploy server nodes at different locations. The ICP may storenetwork resources in different server nodes in a distributed manner, andthe terminal device may access the network resources from the servernodes.

In the embodiments of this application, the server node mayalternatively have another name, for example, a node server, anapplication server, a node device, or a node. This is not limited in theembodiments of the present disclosure, provided that the foregoingmeaning can be expressed.

The ICP in the embodiments of this application is an internet contentprovider for providing a specific network resource, for example,Jingdong, Amazon, Baidu, or Sina. The internet content provider mayalternatively have another name, for example, a content serviceprovider, or a network content provider. In other words, a name of thecontent server is not limited in the embodiments of the presentdisclosure, provided that the foregoing meaning can be expressed.

An internet service provider (ISP) in the embodiments of thisapplication is an operator that provides an internet access service forthe terminal device. In other words, the terminal device accesses anetwork resource in the ICP by using the ISP. The ISP may be ChinaTelecom, China Unicom, China Mobile, Great Wall Broadband Network, orthe like.

For example, the ISP is China Telecom, and the ICP is Baidu. Usually,China Telecom deploys different server nodes at different locations, andBaidu can purchase the server nodes deployed by China Telecom at all thelocations. For example, China Telecom deploys three server nodes inGuangzhou, Shenzhen, and Dongguan. If Baidu purchases the three servernodes, the client may access, by using the three server nodes, networkresources provided by Baidu.

The network resource in the embodiments of this application includes avideo, a picture, a text, or the like. Different ICPs provide differentnetwork resources. For example, Youku is an ICP that provides videoresources.

“At least one” in the present disclosure means one or more. “A pluralityof” in the present disclosure means two or more than two.

In addition, it should be understood that, in the present disclosure,terms such as “first” and “second” are merely used for differentiation,but should not be understood as an indication or implication of relativeimportance or an indication or implication of an order.

Example embodiments provide a server node selection method. In themethod, after a client receives an IP address list fed back by a DNSserver, the client sends connection requests to server nodescorresponding to different IP addresses in the IP address list (theremay be different implementations, which are described below). The clientestablishes a connection to a server node from which the client firstreceives response information fed back by the server node. Generally, ifthe client first receives response information fed back by a specificserver node, it indicates that network quality of the server node iscomparatively good. Therefore, according to the server node selectionmethod provided in the embodiments of this application, a server nodewith comparatively good network quality can be selected from a pluralityof server nodes.

FIG. 2 is a schematic diagram of an application scenario according to anembodiment of this application. As shown in FIG. 2, the applicationscenario includes a mobile phone, a DNS server, and at least one servernode. In FIG. 2, three server nodes are used as an example.

As shown in FIG. 2, the mobile phone sends a domain name resolutionrequest to the DNS server, and the domain name resolution requestcarries a domain name. After receiving the domain name resolutionrequest, the DNS server determines, based on the domain name, one ormore IP addresses corresponding to the domain name, and generates an IPaddress list. For example, the IP address list includes three IPaddresses, and each IP address corresponds to one server node (forexample, an IP 1 corresponds to a server node 1, an IP 2 corresponds toa server node 2, and an IP 3 corresponds to a server node 3). The DNSserver sends the IP address list to the mobile phone.

After receiving the IP address list, the mobile phone sends connectionrequests to the three server nodes. In a first possible implementation,the mobile phone sends a connection request to the server node 1 at amoment t1, sends a connection request to the server node 2 at a momentt1+T, and sends a connection request to the server node 3 at a momentt1+2T. In a second possible implementation, the mobile phonesimultaneously sends the connection requests (not shown in FIG. 2) tothe server node 1, the server node 2, and the server node 3.

The mobile phone establishes a connection to a server node from whichthe mobile phone first receives response information fed back by theserver node. When a next interval T expires, the mobile phone does notsend a connection request to another server node. For example, if themobile phone first receives response information sent by the server node3, the mobile phone establishes a connection to the server node 3. Ifthe IP address list further includes an IP 4 and the IP 4 corresponds toa server node 4, the client does not send a connection request to theserver node 4 at a moment t1+3T. Generally, if the mobile phone firstreceives a specific server node, it indicates that network quality ofthe server node is comparatively good. Therefore, according to theserver node selection method provided in the embodiments of thisapplication, a server node with comparatively good network quality canbe selected from a plurality of server nodes.

To describe the technical solutions in the embodiments of thisapplication more clearly, the following describes a diagram of ahardware structure of a mobile phone in the application scenario shownin FIG. 2. FIG. 3 is a schematic diagram of a hardware structure of amobile phone 300 according to an embodiment of this application. Itshould be understood that the mobile phone 300 shown in FIG. 3 is onlyan example, and the mobile phone 300 may include more or fewercomponents than those shown in the figure, or combine two or morecomponents, or have different component configurations. Variouscomponents shown in FIG. 3 may be implemented in hardware that includesone or more signal processing and/or application-specific integratedcircuits, in software, or in a combination of hardware and software.

As shown in FIG. 3, the mobile phone 300 may specifically includecomponents such as one or more processors 301, a radio frequency (RF)circuit 302, a memory 303, a touchscreen 304, a Bluetooth apparatus 305,one or more sensors 306, a Wi-Fi apparatus 307, a positioning apparatus308, an audio circuit 309, a peripheral interface 310, and a powersupply system 311. These components may communicate with each other byusing one or more communications buses or signal cables (not shown inFIG. 3). A person skilled in the art may understand that the hardwarestructure shown in FIG. 3 does not constitute a limitation on the mobilephone 300, and the mobile phone 300 may include more or fewer componentsthan those shown in the figure, or combine some components, or havedifferent component arrangements.

The following describes in detail all the components of the mobile phone300 with reference to FIG. 3.

The processor 301 is a control center of the mobile phone 300. Theprocessor 301 is connected to all parts of the mobile phone 300 by usingvarious interfaces and lines, and performs various functions of themobile phone 300 and data processing by running or executing anapplication stored in the memory 303 and invoking data and instructionsstored in the memory 303. In some embodiments, the processor 301 mayinclude one or more processing units. The processor 301 may include anapplication processor (AP), a modem processor, and the like. Differentprocessing units included in the processor 301 may be independentdevices, or may be integrated into one processor. For example, theprocessor 301 integrates an application processor and a modem processor.The application processor mainly processes an operating system, a userinterface, an application, and the like. The modem processor mainlyprocesses wireless communication. It can be understood that the modemprocessor may not be integrated into the processor 301.

The radio frequency circuit 302 may be configured to receive and send aradio signal in an information receiving and sending process or in acall process. Specifically, after receiving downlink data from a basestation, the radio frequency circuit 302 may send the downlink data tothe processor 301 for processing, and sends related uplink data to thebase station. Generally, the radio frequency circuit includes but is notlimited to an antenna, at least one amplifier, a transceiver, a coupler,a low noise amplifier, a duplexer, and the like. In addition, the radiofrequency circuit 302 may further communicate with another devicethrough wireless communication. The wireless communication may use anycommunication standard or protocol, including but not limited to aglobal system for mobile communications, a general packet radio service,code division multiple access, wideband code division multiple access,long term evolution, an email, a short message service, and the like.

The memory 303 is configured to store the application program and thedata. The processor 301 performs various functions of the mobile phone300 and data processing by running the application and the data that arestored in the memory 303. The memory 303 mainly includes a programstorage area and a data storage area. The program storage area may storean operating system, and an application required by at least onefunction (for example, a sound play function or an image play function).The data storage area may store data (for example, audio data or a phonebook) created when the mobile phone 300 is used. In addition, the memory303 may include a high-speed random access memory, or may include anonvolatile memory such as a magnetic disk storage device, a flashmemory device, or another nonvolatile solid-state storage device. Thememory 303 may store various operating systems, for example, an iOSoperating system developed by Apple and an Android operating systemdeveloped by Google. For example, the memory 303 stores an applicationrelated to the embodiments of this application, such as Taskcard Store,Twitter, Contacts, or Weibo.

The touchscreen 304 may include a touch-sensitive surface 304-1 and adisplay 304-2. The touch-sensitive surface 304-1 (for example, a touchpanel) may collect a touch event performed by a user of the mobile phone300 on or near the touch-sensitive surface 304-1 (for example, anoperation performed by the user on the touch-sensitive surface 304-1 ornear the touch-sensitive surface 304-1 by using any proper object suchas a finger or a stylus), and send collected touch information toanother component, for example, the processor 301. The display 304-2 maybe configured to display information entered by the user or informationprovided for the user, and various menus of the mobile phone 300. Thedisplay 304-2 may be configured in a form of a liquid crystal display,an organic light-emitting diode, or the like. The touch-sensitivesurface 304-1 may cover the display 304-2. After detecting the touchevent performed on or near the touch-sensitive surface 304-1, thetouch-sensitive surface 304-1 sends the touch event to the processor 301to determine a type of the touch event, and then the processor 301 mayprovide a corresponding visual output on the display 304-2 based on thetype of the touch event. In FIG. 3, the touch-sensitive surface 304-1and the display 304-2 are used as two independent components toimplement input and output functions of the mobile phone 300. However,in some embodiments, the touch-sensitive surface 304-1 and the display304-2 may be integrated to implement the input and output functions ofthe mobile phone 300.

The mobile phone 300 may further include the Bluetooth apparatus 305,configured to implement data exchange between the mobile phone 300 andanother short-distance device (for example, a mobile phone or asmartwatch). In this embodiment of this application, the Bluetoothapparatus may be an integrated circuit, a Bluetooth chip, or the like.

The mobile phone 300 may further include the at least one sensor 306,such as a light sensor, a motion sensor, and another sensor.Specifically, the light sensor may include an ambient light sensor and aproximity sensor. The ambient light sensor may adjust luminance of thedisplay of the touchscreen 304 based on ambient light luminance. Theproximity sensor may power off the display when the mobile phone 300approaches an ear.

In some embodiments of this application, the mobile phone 300 mayfurther include a fingerprint sensor 312. For example, the fingerprintsensor 312 may be disposed on a rear side of the mobile phone 300 (forexample, below a rear-facing camera), or the fingerprint sensor 312 maybe disposed on a front side of the mobile phone 300 (for example, belowthe touchscreen 304). In this embodiment of this application, any typeof sensing technology may be used for the fingerprint sensor 312,including but not limited to an optical sensing technology, a capacitivesensing technology, a piezoelectric sensing technology, an ultrasonicsensing technology, and the like.

The mobile phone 300 may be further provided with another sensor such asa gyroscope, a barometer, a hygrometer, a thermometer, or an infraredsensor. Details are not described herein.

The Wi-Fi apparatus 307 is configured to provide the mobile phone 300with network access that conforms to a Wi-Fi related standard protocol.The mobile phone 300 may access a Wi-Fi access point by using the Wi-Fiapparatus 307, to help the user to receive and send an email, browse aweb page, access streaming media, and the like. The Wi-Fi apparatus 307provides wireless broadband internet access for the user. In some otherembodiments, the Wi-Fi apparatus 307 may alternatively serve as a Wi-Fiwireless access point, and may provide Wi-Fi network access for anotherelectronic device.

The positioning apparatus 308 is configured to provide a geographicallocation for the mobile phone 300. It can be understood that thepositioning apparatus 308 may be specifically a receiver of apositioning system, such as a global positioning system (GPS) or aBeiDou navigation satellite system.

The audio circuit 309, a speaker 313, and a microphone 314 may providean audio interface between the user and the mobile phone 300. The audiocircuit 309 may convert received audio data into an electrical signaland then transmit the electrical signal to the speaker 313, and thespeaker 313 converts the electrical signal into a sound signal foroutput. In addition, the microphone 314 converts a collected soundsignal into an electrical signal. The audio circuit 309 receives theelectrical signal, converts the electrical signal into audio data, andthen outputs the audio data to the RF circuit 302, to send the audiodata to, for example, another mobile phone, or outputs the audio data tothe memory 303 for further processing.

The peripheral interface 310 is configured to provide various interfacesfor an external input/output device (for example, a keyboard, a mouse,an external display, an external memory, or a subscriber identity modulecard). For example, a mouse is connected by using a universal serial businterface, and a subscriber identity module (SIM) card provided by atelecommunications operator is connected by using a metal contact in asubscriber identity module card slot. The peripheral interface 310 maybe configured to couple the external input/output peripheral device tothe processor 301 and the memory 303.

The mobile phone 300 may further include the power supply system 311(for example, a battery and a power management chip) that supplies powerto the components. The battery may be logically connected to theprocessor 301 by using the power management chip, to implement functionssuch as charging and discharging management and power consumptionmanagement by using the power supply system 311.

Behavior of a client in the following embodiments may be implemented ina mobile phone of the foregoing hardware structure.

FIG. 4 is a diagram of a software architecture of the mobile phone 300according to an embodiment of this application. In FIG. 4, an example inwhich the mobile phone 300 is an Android operating system is used. Asshown in FIG. 4, the software architecture of the mobile phone 300includes four layers: a kernel layer, a hardware abstraction layer, anapplication framework layer, and an application layer (applicationslayer). Certainly, in the software architecture shown in FIG. 4, asystem runtime library layer (libraries layer) (not shown in FIG. 4) mayfurther be included between the kernel layer and the applicationframework layer. The system runtime library layer supports an upperlayer, in other words, the framework layer. When the framework layer isused, the Android operating system runs a C/C++ library included in thesystem runtime library layer, to implement a function to be implementedby the framework layer.

The application layer includes various applications, for example, a webbrowser and an instant messaging application (such as WeChat or QQ). Aweb browser is used as an example. The user taps an icon of the browserby using the touch-sensitive surface 304-1 of the mobile phone 300, totrigger the processor 301 to start the browser. The display 304-2displays a display interface of the browser. The user enters a website(for example, http//www.baidu.com) in the display interface by using thetouch-sensitive surface 304-1.

The application framework layer (referred to as a framework layer below)includes OKhttp, and OKhttp is used to encapsulate a website by using atransmission protocol. The transmission protocol includes a transmissioncontrol protocol (TCP), an internet protocol (IP), and the like.

The hardware abstraction layer includes a network daemon (Netd) and alibrary function (Libc for short). Netd is used to connect the kernellayer and the framework layer. Netd may be configured to storeinformation about a DNS server, an IP address of a server node, and thelike, and may be further configured to trigger an RF circuit driver atthe kernel layer.

The kernel layer includes drivers of input/output devices (such as akeyboard, a touchscreen, a headset, a speaker, a microphone, and an RFcircuit).

In some embodiments of this application, an app at the application layerin the mobile phone 300 shown in FIG. 4 may be a client (a browser isused as an example below). OKhttp may be the foregoing DNS query requestdevice. Alternatively, OKhttp, Netd, and Libc together constitute theforegoing DNS query request device. To be specific, OKhttp completesprocesses such as DNS resolution request sending, IP address receiving,and server node selection and connection with the assistance of Netd andLibc. The following describes a process of implementing, by using themobile phone shown in FIG. 3 and FIG. 4, a server node selection methodprovided in the embodiments of this application.

It should be understood that FIG. 3 shows the hardware architecture ofthe mobile phone 300 according to the embodiment of this application,and FIG. 4 shows the software architecture of the mobile phone 300according to the embodiment of this application. Therefore, a softwareprogram and/or module corresponding to the software architecture in FIG.4 may be stored in the memory 303, and the processor 301 runs thesoftware program and/or module stored in the memory 303, to perform thefollowing process:

(1) A browser at the application layer is used as an example. Thebrowser sends, to OKhttp at the framework layer, a website, in otherwords, a URL, entered by the user (the foregoing content has describedthe process in which a user enters a website in a display interface of abrowser, and details are not described herein again). After receivingthe website sent by the browser, OKhttp extracts a domain name from thewebsite, and OKhttp sends the extracted domain name to Netd.

(2) After receiving the domain name, Netd obtains a domain nameresolution request based on a DNS resolution command, and sends thedomain name resolution request to the DNS server. For example, Netdinvokes the RF circuit driver to start the RF circuit, and the RFcircuit sends the domain name resolution request to the DNS server. Forexample, Netd may store the information about the DNS server. Forexample, Netd stores geographical locations of a plurality of DNSservers. After receiving the domain name resolution request, Netd maydetermine a DNS server closest to a current geographical location of themobile phone 300 from the plurality of DNS servers, and the RF circuitsends the domain name resolution request to the determined DNS server.

(3) After receiving an IP address list returned by the DNS server, theRF circuit returns the IP address list to Netd. Netd returns the IPaddress list to Okhttp. Okhttp generates a first handshake request. Thefirst handshake request is used to request to establish a connection toa first server node, and an IP address of the first server node is afirst IP address in the IP address list. Okhttp sends the firsthandshake request to Libc. Libc invokes the RF circuit driver to startthe RF circuit. The RF circuit sends the first handshake request to thefirst server node.

(4) Okhttp starts timing. If Okhttp does not receive, within a firstpreset time, response information fed back by the first server node,Okhttp generates a second handshake request. The second handshakerequest is used to request to establish a connection to a second servernode, and an IP address of the second server node is a second IP addressin the IP address list. Okhttp sends the second handshake request toLibc. Libc invokes the RF circuit driver to start the RF circuit. The RFcircuit sends the second handshake request to the second server node.

(5) Assuming that Okhttp first receives the response information fedback by the first server node, Okhttp sends a network resource request(for example, the network resource request may be extracted from theURL, and the network resource request may be /?fr=mhd_card if the URL iswww.baidu.com/?fr=mhd_card) to the first server node. For example,Okhttp may invoke Libc, Libc invokes the RF circuit driver to start theRF circuit, the RF circuit sends the network resource request to thefirst server node, the RF circuit sends a network resource to Libc whenreceiving the network resource fed back by the first server node, Libcsends the network resource to Okhttp, and Okhttp sends the networkresource to the browser.

An example in which the mobile phone 300 sends connection requests tothe first server node and the second server node at a specific timeinterval is used in the foregoing steps (1) to (5). Actually, the mobilephone 300 may alternatively send connection requests to the first servernode and the second server node simultaneously.

Details are not described herein.

FIG. 5 is a schematic flowchart of a server node selection methodaccording to an embodiment of this application. The method is applied tothe application scenario shown in FIG. 2. It should be noted that stepsperformed by the mobile phone 300 in FIG. 5 may be performed by a DNSquery request device (for example, OKhttp in the mobile phone).

As shown in FIG. 5, the procedure includes the following steps.

S501: The mobile phone 300 sends a domain name resolution request to theDNS server, where the domain name resolution request carries a domainname, and the domain name resolution request is used to request toresolve an IP address corresponding to the domain name. Correspondingly,the DNS server receives the domain name resolution request sent by themobile phone 300.

Before sending the domain name resolution request to the DNS, the mobilephone 300 may select one DNS server from a plurality of DNS servers, andsend the domain name resolution request to the selected DNS server. Aprocess in which the mobile phone 300 selects a DNS server and sends thedomain name resolution request to the DNS server is described above, anddetails are not described herein again. Certainly, the mobile phone 300may alternatively not select a DNS server, in other words, send thedomain name resolution request to the DNS servers, receive IP addresslists sent by the DNS servers, and integrate the IP address lists sentby the DNS servers into one IP address list, to perform a subsequentprocess.

Usually, one domain name corresponds to a relatively large quantity ofIP addresses. Therefore, after determining a plurality of IP addressesbased on a domain name, the DNS server may select some IP addresses fromthe plurality of IP addresses, and send the selected IP addresses to themobile phone 300. For example, the DNS server may record current visitsof a server node corresponding to each IP address, select a server nodewith fewer current visits from a plurality of server nodes, and send theselected server node to the mobile phone 300.

S502: The DNS server sends an IP address list to the mobile phone 300,where the IP address list includes one or more IP addresses, and the oneor more IP addresses are IP addresses that are determined by the DNSserver based on the domain name and that correspond to the domain nameCorrespondingly, the mobile phone 300 receives the IP address list sentby the DNS server.

For example, Table 1 shows a possible IP address list (Table 1 is merelyan example, and does not limit the IP address list).

TABLE 1 Server node IP address Domain name Server node 1 114.115.190.71baidu.com Server node 2 114.171.121.50 baidu.com Server node 3114.129.133.20 baidu.com

Actually, the DNS server may not send an IP address to the mobile phone300 in a form of a table, but send the IP address in another manner. Forexample, the DNS server sends all IP addresses to the mobile phone 300through packing. This is not limited in the embodiments of the presentdisclosure.

S503: The mobile phone 300 sends a first connection request to a firstserver node at a first moment t1, where the first connection request isused to request to establish a connection to the first server node, andthe first server node is a server node corresponding to an IP address inthe IP address list.

Table 1 is used as an example, and an example in which the first servernode is the server node 1 in Table 1 is used. Usually, the mobile phone300 may establish the connection to the first server node through athree-way handshake. A detailed process is as follows:

(1) First handshake: The mobile phone 300 sends a first handshakerequest to the first server node. The first handshake request carries aflag bit “SYN=1” and an initial sequence number “seq=x”. The flag bitSYN is set to 1, and is used to indicate that the mobile phone 300enters a SYN-sent state. The sequence number “seq=x” is randomlygenerated by the mobile phone 300, and is used in a subsequent handshakeprocess.

(2) Second handshake: After receiving the first handshake request sentby the mobile phone 300, the first server node learns, from the flag bit“SYN=1” in the first handshake request, that the mobile phone 300requests to establish the connection. If the first server node agrees toestablish the connection, the first server node sends ACK information(for ease of description, the ACK information is referred to as a secondhandshake request below) to the mobile phone 300. The ACK messagecarries the flag bit “SYN=1”, an acknowledgment number “ack=x+1”, and asequence number seq=y that is randomly generated. The flag bit “SYN=1”is used to indicate that the first server node enters a SYN-receivedstate. The acknowledgment number is generated by the first server nodebased on “seq=x” in the first handshake request. The first server noderandomly generates the value “seq=y”, which is used in a subsequenthandshake process.

(3) Third handshake: After receiving the ACK information (that is, thesecond handshake request) sent by the first server node, the mobilephone 300 sends acknowledgment information (for ease of description, theacknowledgment information is referred to as a third handshake requestbelow) to the first server node. The acknowledgment information includesan acknowledgment number “ack=y+1” and a sequence number “seq=x+1”. Themobile phone 300 enters an established state. After receiving theacknowledgment information, the first server node also enters anestablished state.

After the steps (1) to (3) are completed, the mobile phone 300establishes the connection to the first server node. It can be learnedthat, in the process in which the mobile phone 300 establishes theconnection to the first server node, the mobile phone 300 sendsinformation to the first server node twice, that is, the first handshakerequest and the third handshake request.

Therefore, in this embodiment of this application, the first connectionrequest sent by the mobile phone to the first server node at the firstmoment in S503 may be the first handshake request. If the firstconnection request is the first handshake request, response informationfed back by the first server node may be response information for thefirst handshake request, that is, the ACK information (that is, thesecond handshake request) sent by the first server node to the mobilephone 300 in the second handshake process. In this case, after receivingthe response information sent by the first server node, the mobile phone300 may further send the third handshake request to the first servernode, to complete the process in which the mobile phone 300 establishesthe connection to the first server node, and then the mobile phone 300sends a network resource request to the first server node to request anetwork resource.

S504: If the mobile phone 300 does not receive, within a first presetduration T, the response information fed back by the first server node,the mobile phone 300 sends a second connection request to a secondserver node at a second moment (a moment t 1+T). The second server nodeis a server node corresponding to another IP address in the IP addresslist.

Table 1 is used as an example. If the first server node is the servernode 1, the second server node may be the server node 2 or the servernode 3.

In this embodiment of this application, the mobile phone 300 sets thefirst preset duration T. A specific value of the first preset duration Tis not limited in the embodiments of the present disclosure.

If the mobile phone 300 receives, within the first preset duration T,the response information fed back by the first server node, the mobilephone 300 establishes the connection to the first server node to requestthe network resource from the first server node, and does not send thesecond connection request to the second service node at the secondmoment.

S505: If the mobile phone 300 first receives, within the first presettime T after the second moment, the response information sent by thefirst server node, the mobile phone 300 establishes the connection tothe first server node.

It should be noted that, it can be learned from the foregoing contentthat the first connection request may be the first handshake request.Therefore, the response information fed back by the first server nodemay be response information for the first handshake request, that is,the ACK information (that is, the second handshake request) sent by thefirst server node to the mobile phone 300 in the second handshakeprocess. In this case, after receiving the response information sent bythe first server node, the mobile phone 300 may further send the thirdhandshake request to the first server node, to complete the process inwhich the mobile phone 300 establishes the connection to the firstserver node, and then the mobile phone 300 sends a network resourcerequest to the first server node to request a network resource.

S506: The mobile phone 300 sends the network resource request to thefirst server node, where the network resource request is used to requesta network resource.

S507: The mobile phone 300 receives the network resource returned by thefirst server node.

Baidu is used as an example. Baidu may store a network resource in eachdeployed server node, or may store a network resource in a cloud storageserver. Therefore, after the first server node receives the networkresource request sent by the mobile phone 300, if the first server nodestores the network resource requested by the network resource request,the first server node sends the network resource to the mobile phone300. If the first server node does not store the network resourcerequested by the network resource request, the first server node mayobtain the network resource from the cloud storage server. Afterobtaining the network resource, the first server node sends the networkresource to the mobile phone 300.

It can be learned from the foregoing description that, in thisembodiment of this application, if there are a relatively large quantityof IP addresses in the IP address list (in other words, there are arelatively large quantity of server nodes), the mobile phone 300 maysend the first connection request to the first server node at the firstmoment. If the mobile phone 300 receives, within the first presetduration T, the response information fed back by the first server node,the mobile phone 300 requests to establish the connection to the firstserver node to request the network resource, and does not send aconnection request to another server node. If the mobile phone 300 doesnot receive, within the first preset duration T after the first moment,the response information fed back by the first server node, when thefirst preset duration expires, the mobile phone 300 sends the secondconnection request to the second server node at the second moment. Ifthe mobile phone 300 receives, within the first preset duration T afterthe second moment, the response information fed back by the first servernode or response information fed back by the second server node, themobile phone 300 establishes a connection to a server node correspondingto earlier received response information, to request the networkresource, and does not send a connection request to the other servernode. If the mobile phone 300 does not receive, within the first presetduration after the second moment, the response information fed back bythe first server node or response information fed back by the secondserver node, when the first preset duration after the second momentexpires, the mobile phone 300 sends a third connection request to athird server node at a third moment, and so on. If the mobile phone 300has sent a connection request to each server node once, but does notreceive response information fed back by any server node, the mobilephone 300 may continue to send a connection request to the first servernode, in other words, perform S503 again. Alternatively, the mobilephone 300 may perform S501 again, notify the DNS server that all servernodes in the IP address list fed back last time cannot be connected, andrequest the DNS server to send a new IP address list to the mobile phone300.

It can be learned from the foregoing description that, in the solutionof this embodiment of this application, after obtaining a plurality ofIP addresses, the mobile phone 300 may not simultaneously sendconnection requests to server nodes corresponding to the plurality of IPaddresses, but send connection requests to server nodes corresponding todifferent IP addresses at a specific interval. For example, the IPaddress list fed back by the DNS server includes three IP addresses. Ifthe mobile phone 300 simultaneously sends connection requests to servernodes corresponding to the three IP addresses, a resource waste iscaused for the mobile phone. For example, when sending a request to aserver node corresponding to one IP address, the mobile phone needs tocreate one socket. In this case, when simultaneously sending theconnection requests to the server nodes corresponding to the three IPaddresses, the mobile phone needs to simultaneously create threesockets. However, in this embodiment of this application, the mobilephone first sends a connection request to the server node 1 at the firstmoment, in other words, the mobile phone first creates a socket. If themobile phone 300 does not receive, within the first preset duration T,response information fed back by the server node 1, the mobile phonecreates another socket, and sends a connection request to the servernode 2 at the second moment. When the mobile phone first receives thefeedback information from the server node 1 within the first presetduration after the second moment, the mobile phone establishes aconnection to the server node 1. In this case, the mobile phone maydisconnect the socket of the server node 2. It can be learned that themobile phone does not need to simultaneously create respective socketsof the three server nodes, thereby saving resources. In addition, themobile phone simultaneously sends the connection requests to the servernodes corresponding to the three IP addresses, and consequently anetwork load is increased, and a relatively large quantity of networkresources are occupied in a short time. However, the mobile phone 300sends connection requests to server nodes corresponding to different IPaddresses at a specific interval, so that the connection requests aresent separately. Therefore, a network load is not increased within aperiod of time. In addition, the mobile phone 300 does not necessarilyneed to send connection requests to server nodes corresponding to all IPaddresses. Therefore, few network resources are consumed, and an optimalserver node can be quickly connected without increasing concurrentvisits.

The following lists two examples to describe the server node selectionmethod shown in FIG. 5.

Example 1

FIG. 6 is a schematic flowchart of a routing selection method accordingto an embodiment of this application. In FIG. 6, the applicationscenario shown in FIG. 2 is used as an example, and an example in whicht1 is 0 ms and T is 100 ms is used.

After the mobile phone 300 sends a domain name resolution request to theDNS server (S601), the DNS server obtains a domain name throughresolution, to obtain an IP address list, and sends the IP address listto the mobile phone 300 (S602). The mobile phone 300 sends a firstconnection request to the server node 1 at a moment of 0 ms (S603). Whenthe mobile phone 300 does not receive, within 100 ms, responseinformation fed back by the server node 1, the mobile phone 300 sends asecond connection request to the server node 2 at a moment of 100 ms(S604). The mobile phone 300 establishes a connection to a server nodefrom which the mobile phone 300 first receives, within 100 ms after themobile phone 300 sends the connection requests to the server node 1 andthe server node 2, response information fed back by the server node.

Still referring to FIG. 6, the mobile phone 300 receives, at a moment of120 ms, the response information fed back by the server node 1 (S605),but does not receive, before or at the moment of 120 ms, responseinformation fed back by the server node 2. To be specific, the mobilephone 300 first receives the response information fed back by the servernode 1, and therefore the mobile phone 300 establishes a connection tothe server node 1.

It should be noted that, after receiving the response information fedback by the server node 1, the mobile phone 300 may subsequently receivethe response information fed back by the server node 2. For example, ifthe mobile phone 300 subsequently receives the response information fedback by the server node 2, the mobile phone 300 may not respond to ormay discard the response information fed back by the server node 2.Still referring to FIG. 6, the mobile phone 300 receives, at a moment of130 ms, the response information fed back by the server node 2 (S606).Because the mobile phone 300 has established the connection to theserver node 1, the mobile phone 300 may not respond to or may discardthe response information fed back by the server node 2. For example,when the mobile phone 300 receives response information fed back by oneserver node, it may be determined whether the mobile phone 300 hasestablished a connection to a specific server node. If the mobile phone300 has established the connection to the specific server node, themobile phone 300 may not respond to or may discard response informationfed back by the one server node.

For another example, to save resources, after receiving the responseinformation fed back by the server node 1, the mobile phone 300 may notreceive the response information fed back by the server node 2. Forexample, the mobile phone 300 may disconnect a socket corresponding tothe server node 2. It should be noted that, when the mobile phone 300sends a connection request to the server node 1, the mobile phone 300creates a socket between the mobile phone 300 and the server node 1, tosend the connection request to the server node 1 by using the socket.This is similar to a process in which the mobile phone 300 sends aconnection request to the server node 2. Therefore, after the mobilephone 300 receives the response information fed back by the server node1, the mobile phone 300 may disconnect the socket corresponding to theserver node 2, and does not receive the response information of theserver node 2, thereby saving resources.

Still referring to FIG. 6, after the mobile phone 300 establishes theconnection to the server node 1, the mobile phone 300 may request anetwork resource from the server node 1 (S607). The server node 1 feedsback the network resource to the mobile phone 300 (S608).

It should be noted that, in Example 1, the mobile phone 300 sends theconnection request to the server node 1 at the moment of 0 ms, andreceives, at a moment of 120 ms, the response information sent by theserver node 1. In other words, a response time of the server node 1 is120 ms. The mobile phone 300 sends the connection request to the servernode 2 at the moment of 100 ms, and receives, at a moment of 130 ms, theresponse information sent by the server node 2. In other words, aresponse time of the server node 2 is 30 ms. It can be learned that,although the response time of the server node 2 is less than theresponse time of the server node 1, the mobile phone 300 still selectsto connect to the server node 1. Because a server node whose responsetime ranges from T to 2T (100 ms to 200 ms) has comparatively goodnetwork quality, after the mobile phone 300 first receives the responseinformation fed back by the server node 1, the mobile phone 300considers that the server node 1 has comparatively good network quality.Therefore, the mobile phone 300 may directly establish the connection tothe server node 1, and does not need to establish a connection to theserver node 2 after waiting for 10 ms to receive the responseinformation fed back by the server node 2, thereby saving 10 ms (forexample, within 10 ms, the mobile phone 300 may complete a process ofsending a network resource request to the server node 1).

In Example 1, because the mobile phone 300 has received, within 120 ms,the response information fed back by the server node 1, the mobile phone300 does not need to send a third connection request (represented by adashed line in the figure) to the server node 3 at a moment of 200 ms.If the mobile phone 300 does not receive, within 200 ms, the responseinformation fed back by the server node 1 or the server node 2, themobile phone 300 sends the connection request to the server node 3 atthe moment of 200 ms. The mobile phone 300 establishes a connection to aserver node from which the mobile phone 300 first receives, within 200ms to 300 ms response information fed back by the server node.

Example 2

FIG. 7 is a schematic flowchart of a server node selection methodaccording to an embodiment of this application. In FIG. 7, theapplication scenario shown in FIG. 2 is used as an example, and anexample in which t1 is 0 ms and T is 100 ms is used.

In Example 2, a process in which the mobile phone 300 sends connectionrequests to the server node 1 and the server node 2 (S701 to S704) issimilar to that in Example 1 (S601 to S604). For brevity of thisspecification, details are not described herein again.

If the mobile phone 300 first receives, within T to 2T, responseinformation fed back by the server node 1, the mobile phone 300 may notestablish a connection to the server node 1 temporarily, but wait forsecond preset duration. As shown in FIG. 7, the mobile phone 300receives, within 120 ms, the response information fed back by the servernode 1 (S705), and the mobile phone 300 may not establish the connectionto the server node 1 temporarily, but wait for the second presetduration. The second preset duration may be less than T.

For example, the second preset duration may be: T (duration in which theserver node 1 feeds back the response information). When the mobilephone 300 receives, within 120 ms, the response information fed back bythe server node 1, the mobile phone 300 may wait for duration of 80 ms.If the mobile phone 300 does not receive, before a moment of 200 ms,response information fed back by the server node 2, the mobile phone 300establishes the connection to the server node 1. Alternatively, if themobile phone 300 receives, before a moment of 200 ms, responseinformation fed back by the server node 2 (S706), the mobile phone 300establishes a connection to the server node 2 because a response time ofthe server node 2 is shorter (a response time of the server node 1 is120 ms, and the response time of the server node 2 is less than 100 ms).

For another example, the second preset duration may alternatively be:T+a common duration in which a server node feeds back responseinformation a duration in which the server node 1 feeds back theresponse information. Usually, a duration from a moment at which themobile phone sends a connection request to a server node to a moment atwhich the mobile phone receives response information fed back by theserver node is 40 ms to 50 ms. For example, a duration in which a servernode feeds back response information is usually 50 ms. Because themobile phone 300 sends a connection request to the server node 2 at amoment of 100 ms, there is a relatively high probability that the mobilephone 300 receives, within 150 ms, the response information fed back bythe server node 2. Therefore, when the mobile phone 300 receives, within120 ms, the response information fed back by the server node 1, themobile phone 300 may wait for 30 ms. If the mobile phone 300 does notreceive, before a moment of 150 ms, the response information fed back bythe server node 2, the mobile phone 300 may establish the connection tothe server node 1. If the mobile phone 300 receives, within 30 ms, theresponse information fed back by the server node 2, the mobile phone 300establishes the connection to the server node 2 (because a response ofthe server node 2 is quicker than a response of the server node 1, wherea response time of the server node 1 is 120 ms, and a response time ofthe server node 2 is 50 ms).

If the mobile phone 300 first receives, within T to 2T, the responserequest fed back by the server node 2, the mobile phone 300 mayestablish the connection to the server node 2, and does not need to waitfor the second preset duration. Because the mobile phone 300 first sendsthe connection request to the server node 1 and then sends theconnection request to the server node 2, when the mobile phone 300 firstreceives, within T to 2T, the response information fed back by theserver node 2, in other words, when the server node 2 respondscomparatively quickly, the mobile phone 300 may directly establish theconnection to the server 2.

Example 3

FIG. 8 is a schematic flowchart of a routing selection method accordingto an embodiment of this application. In FIG. 8, the applicationscenario shown in FIG. 2 is used as an example, and an example in whicht1 is 0 ms and T is 100 ms is used.

After the mobile phone 300 sends a domain name resolution request to theDNS server (S801), the DNS server obtains a domain name throughresolution, to obtain an IP address list, and sends the IP address listto the mobile phone 300 (S802). The mobile phone 300 sends a firstconnection request to the server node 1 at a moment of 0 ms (S803). Whenthe mobile phone 300 does not receive, within 100 ms, responseinformation fed back by the server node 1, the mobile phone 300 sends asecond connection request to the server node 2 at a moment of 100 ms(S804).

The mobile phone 300 simultaneously receives, within 150 ms, theresponse information fed back by the server node 1 and responseinformation fed back by the server node 2 (S805). The followingdescribes a processing manner of the mobile phone 300 when the mobilephone 300 simultaneously receives response information fed back by twoserver nodes.

In a first possible implementation, after receiving the responseinformation fed back by the server node 1 and the response informationfed back by the server node 2, the mobile phone 300 may first processone piece of response information (for example, the mobile phone 30 mayrandomly select one piece of response information for processing). Ifthe mobile phone 300 first processes the response information fed backby the server node 1, the mobile phone 300 may directly establish aconnection to the server node 1. In this case, the mobile phone 300 maynot need to process the response information fed back by the server node2, or may discard the response information fed back by the server node2.

In this manner, when the mobile phone 300 simultaneously receives twopieces of response information, the mobile phone 300 establishes aconnection to a server node corresponding to response information thatis first processed. A reason is as follows: It can be learned from theforegoing content that a server node whose response time ranges from Tto 2T (100 ms to 200 ms) has comparatively good network quality.Therefore, after the mobile phone 300 simultaneously receives theresponse information fed back by the server node 1 and the responseinformation fed back by the server node 2, it is considered that boththe server node 1 and the server node 2 have comparatively good networkquality. Therefore, the mobile phone 300 establishes a connection to aserver node whose response information fed back by the server node isfirst processed by the mobile phone 300.

In a second possible implementation, after the mobile phone 300simultaneously receives the two pieces of response information, themobile phone 300 may first determine specific server nodes thatrespectively send the two pieces of response information, and the mobilephone 300 may select a server node with a comparatively short responsetime and establish a connection to the server node.

For example, the mobile phone 300 may record a first moment at which thefirst connection request is sent to the server node 1, and record asecond moment at which the response information sent by the server node1 is received. A time difference between the first moment and the secondmoment is a response time of the server node 1. A response time of theserver node 2 is also calculated in a similar manner, and details arenot described again. The mobile phone 300 receives the two pieces ofresponse information, and determines, based on identifiers of the servernodes carried in the two pieces of response information, specific servernodes that respectively send the two pieces of response information.Because the response time (50 ms) of the server node 2 is less than theresponse time (150 ms) of the server node 1, the mobile phone 300establishes a connection to the server node 2. In this case, the mobilephone 300 may not process or may discard the response information fedback by the server node 1.

In a third possible implementation, after the mobile phone 300simultaneously receives the two pieces of response information, themobile phone 300 may first determine specific server nodes respectivelycorresponding to the two pieces of response information, and the mobilephone 300 establishes a connection to a server node to which the mobilephone 300 first sends a connection request.

For example, the mobile phone 300 may record a time or a sequence ofsending connection requests to the server node 1 and the server node 2.For example, in FIG. 8, the mobile phone 300 first sends the connectionrequest to the server node 1, and then sends the connection request tothe server node 2. Therefore, after receiving the two pieces of responseinformation, the mobile phone 300 may establish the connection to theserver node 1. In this case, the mobile phone 300 may not process or maydiscard the response information fed back by the server node 2.

The foregoing several implementations are merely examples, and there maybe another implementation during actual application. This is not limitedin the embodiments of the present disclosure.

In this embodiment of this application, after the mobile phone 300establishes the connection to the first server node in the IP addresslist, the first server node may also be faulty. FIG. 7 is used as anexample. After the mobile phone 300 establishes the connection to theserver node 1, the server node 1 may be faulty. Consequently, aftersending a network resource request to the server node 1, the mobilephone 300 cannot receive, for a long time, a network resource fed backby the server node 1. Therefore, the following describes the processingmanner of the mobile phone 300 after the server node 1 is faulty.

In a first possible implementation, the mobile phone 300 may record aresponse time of receiving each server node. After the first server nodeis faulty, the mobile phone 300 may re-determine the second server nodebased on the recorded response time of each server node and establish aconnection to the second server node. FIG. 7 is used as an example. Theresponse time of the server node 1 is 120 ms, and the response time ofthe server node 2 is 30 ms. When the server node 1 is faulty after themobile phone 300 establishes the connection to the server node 1, themobile phone 300 may establish the connection to the server node 2, andsend the network resource request to the server node 2. This mannerreduces a delay of obtaining a network resource by the mobile phone 300.

In a second possible implementation, after the mobile phone 300 isconnected to the server node 1, if the server node 1 is faulty, themobile phone 300 may also perform the procedure shown in FIG. 5 again.Because the server node 1 is faulty, when the mobile phone 300 performsthe procedure shown in FIG. 5, the mobile phone 300 may directly sendthe second connection request to the server node 2 without a need ofsending the first connection request to the server node 1, and does notreceive, within the duration T, the response information fed back by theservice node 2. In this case, the mobile phone 300 sends a thirdconnection request to a service node 3, and select one server node fromthe server node 2 and the server node 3.

In the embodiments shown in FIG. 5 to FIG. 8, the mobile phone 300 sendsconnection requests to the server nodes 1 to 3 at a specific timeinterval. Actually, the mobile phone 300 may alternativelysimultaneously send connection requests to the server nodes 1 to 3. FIG.9 is a schematic flowchart of another server node selection methodaccording to an embodiment of this application. In the method, themobile phone 300 simultaneously sends connection requests to the servernodes 1 to 3 (S903), and the mobile phone 300 first receives responseinformation fed back by the server node 1 (S904). Therefore, the mobilephone 300 establishes a connection to the server node 1.

It should be noted that various implementations in the embodiment shownin FIG. 9 and the embodiments shown in FIG. 5 to FIG. 8 may be combinedto achieve different technical effects. For example, in the embodimentshown in FIG. 9, if the mobile phone 300 simultaneously receivesresponse information fed back by the server nodes 1 to 3, processing maybe performed in the processing manner in the embodiment shown in FIG. 7.

In this embodiment of this application, after selecting the first servernode to establish the connection and requesting a network resource fromthe first server node, the mobile phone 300 may store a domain name in aURL and an IP address of the first server node for a period of time. Inthis period of time, if the mobile phone 300 re-initiates another URL,if a domain name carried in the URL is the same as the stored domainname, and a time in which the mobile phone 300 re-initiates another URLdoes not exceed the period of time, the mobile phone 300 directly sendsa network resource request corresponding to the another URL to the firstserver node, without a need of performing the procedure shown in FIG. 5,so as to request a network resource. If the time in which the mobilephone 300 re-initiates another URL exceeds the period of time, themobile phone 300 may perform the procedure shown in FIG. 5 again. Inthis case, the mobile phone 300 may delete the domain name and the IPaddress of the first server node. The mobile phone 300 performs theprocedure shown in FIG. 5 again. After establishing a connection to aspecific server node, the mobile phone 300 stores the domain name and anIP address of the server node for a period of time again.

A person skilled in the art may determine, based on an actual situation,a period of time for storing the domain name and the IP address of thefirst server node, for example, 10 minutes.

The following describes, by using an example, the technical effectsimplemented by using the server node selection methods provided in theembodiments of this application.

FIG. 10 is a schematic diagram of a process of testing a three-wayhandshake between a client and a fault-free server node. An IP addressof the client is 100.65.147.165, and an IP address of the fault-freeserver node is 114.115.190.71. The first row is a first handshakeprocess, the second row is a second handshake process, and the third rowis a third handshake process. The first column indicates a time, thesecond column indicates a TCP protocol, the third column indicates atransmit end, and the fourth column indicates a receive end. As shown inFIG. 8, in the first row, at a moment of 4.331427 s, the client (thetransmit end) sends a first handshake request to the fault-free servernode (the receive end). In the second row, at a moment of 4.375664 s,the fault-free server node (the transmit end) sends response information(that is, a second handshake request) to the client (the receive end).In the third row, at a moment of 4.375785 s, the client (the transmitend) sends a third handshake request to the fault-free server node (thereceive end), and so on, until the client establishes a connection tothe fault-free server node. For example, the first connection requestshown in FIG. 5 is the first handshake request. To be specific, aduration from a moment at which the mobile phone 300 sends the firsthandshake request to a moment at which the mobile phone 300 receives thesecond handshake request is: 4.375664 4.331427=44 ms. It can be learnedthat a period of time consumed from a moment at which the mobile phone300 sends a connection request to the server node 1 to a moment at whichthe mobile phone 300 receives response information fed back by theserver node is within 40 ms to 50 ms.

In other words, if the server node 1 is a fault-free server node, themobile phone 300 may receive, within 40 ms to 50 ms, responseinformation fed back by the server node 1. In the foregoing examples (6Ato 6C, and 7), an example in which T is 100 ms is used. Therefore, thereis a relatively low probability that the mobile phone 300 cannotreceive, within 100 ms, the response information fed back by the servernode 1. It is assumed that the probability is 10%, in other words, themobile phone 300 has a probability of 10% to send a second connectionrequest to the server node 2. For the server node 2, if the server node2 is not faulty, a probability that the mobile phone 300 cannot receive,within 100 ms, the response information fed back by the server node 2 isalso 10%, in other words, the mobile phone 300 has only a probability of10%*10%=1% to send a third connection request to the server node 3. Ifthere are a large quantity of server nodes, the rule may be followed.

It can be learned that a probability that the client tries a new servernode gradually decreases, in other words, a probability that the clientfinds a proper server node after trying a plurality of server nodes isrelatively low. In addition, after the client fails to try a firstserver node, a time difference between a moment of trying the firstserver node and a moment of trying a second server node is 100 ms, whichis relatively short and is not obviously perceived by a user. In otherwords, in a user perception-free case, the mobile phone 300 alreadytries to establish a connection to the second server node. This helpsimprove user experience.

The implementations of this application may be randomly combined toachieve different technical effects.

In the foregoing embodiments provided in this application, the methodsprovided in the embodiments of this application are described from theperspective of using a client as an execution body. To implementfunctions in the methods provided in the embodiments of thisapplication, the client may include a hardware structure and/or asoftware module, and implement the foregoing functions in a form of thehardware structure, the software module, or a combination of thehardware structure and the software module. Whether a function in theforegoing functions is performed in a manner of the hardware structure,the software module, or the combination of the hardware structure andthe software module depends on particular applications and designconstraints of the technical solutions.

Based on a same concept, FIG. 11 shows a terminal device 1100 accordingto an embodiment of this application. As shown in FIG. 11, the terminal1100 may include a transmitter 1101, a receiver 1102, and a processor1103. The transmitter 1101, the receiver 1102, and the processor 1103may be connected by using one or more communications buses. Certainly,during actual application, the transmitter 1101, the receiver 1102, andthe processor 1103 may not be of a bus structure, but may be of anotherstructure, for example, a star structure. This is not specificallylimited in the embodiments of the present disclosure.

The transmitter 1101 may be configured to perform S501, S504, S503, andS506 in the embodiment shown in FIG. 5, and/or configured to supportanother process of the technology described in this specification.Alternatively, the transmitter 1101 may be configured to perform S601,S603, S604, and S607 in the embodiment shown in FIG. 6, and/orconfigured to support another process of the technology described inthis specification. Alternatively, the transmitter 1101 may beconfigured to perform S701, S703, S704, and S707 in the embodiment shownin FIG. 7, and/or configured to support another process of thetechnology described in this specification. Alternatively, thetransmitter 1101 may be configured to perform S801, S803, S804, and S806in the embodiment shown in FIG. 8, and/or configured to support anotherprocess of the technology described in this specification.Alternatively, the transmitter 1101 may be configured to perform S901,S903, and S906 in the embodiment shown in FIG. 9, and/or configured tosupport another process of the technology described in thisspecification.

The receiver 1102 is configured to perform S502, S505, and S507 in theembodiment shown in FIG. 5, and/or configured to support another processof the technology described in this specification. Alternatively, thereceiver 1102 is configured to perform S602, S605, S606, and S608 in theembodiment shown in FIG. 6, and/or configured to support another processof the technology described in this specification. Alternatively, thereceiver 1102 is configured to perform S702, S705, S706, and S708 in theembodiment shown in FIG. 7, and/or configured to support another processof the technology described in this specification. Alternatively, thereceiver 1102 is configured to perform S802, S805, and S807 in theembodiment shown in FIG. 8, and/or configured to support another processof the technology described in this specification. Alternatively, thereceiver 1102 is configured to perform S902, S904, S905, and S907 in theembodiment shown in FIG. 9, and/or configured to support another processof the technology described in this specification.

The processor 1103 is configured to trigger to send a connectionrequest, and select a server node based on response information, so asto establish a connection to obtain a network resource.

Based on a same concept, FIG. 12 shows a terminal device 1200 accordingto an embodiment of this application. As shown in FIG. 9, the terminal1200 may include a sending unit 1201, a processing unit 1203, and areceiving unit 1202. The processing unit 1203 may be OKhttp in FIG. 4,and the sending unit 1201 and the receiving unit 1202 may be Netd orLibc.

The sending unit 1201 may be configured to perform S501, S503, S504, andS506 in the embodiment shown in FIG. 5, and/or configured to supportanother process of the technology described in this specification.Alternatively, the sending unit 1201 may be configured to perform S601,S603, S604, and S607 in the embodiment shown in FIG. 6, and/orconfigured to support another process of the technology described inthis specification. Alternatively, the sending unit 1201 may beconfigured to perform S701, S703, S704, and S707 in the embodiment shownin FIG. 7, and/or configured to support another process of thetechnology described in this specification. Alternatively, the sendingunit 1201 may be configured to perform S801, S803, S804, and S806 in theembodiment shown in FIG. 8, and/or configured to support another processof the technology described in this specification. Alternatively, thesending unit 1201 may be configured to perform S901, S903, and S906 inthe embodiment shown in FIG. 9, and/or configured to support anotherprocess of the technology described in this specification.

The receiving unit 1202 is configured to perform S502, S505, and S507 inthe embodiment shown in FIG. 5, and/or configured to support anotherprocess of the technology described in this specification.Alternatively, the receiving unit 1202 is configured to perform S602,S605, S606, and S608 in the embodiment shown in FIG. 6, and/orconfigured to support another process of the technology described inthis specification. Alternatively, the receiving unit 1202 is configuredto perform S702, S705, S706, and S708 in the embodiment shown in FIG. 7,and/or configured to support another process of the technology describedin this specification. Alternatively, the receiving unit 1202 isconfigured to perform S802, S805, and S807 in the embodiment shown inFIG. 8, and/or configured to support another process of the technologydescribed in this specification. Alternatively, the receiving unit 1202is configured to perform S902, S904, S905, and S907 in the embodimentshown in FIG. 9, and/or configured to support another process of thetechnology described in this specification.

The processing unit 1203 is configured to trigger to send a connectionrequest, and select a server node based on response information, so asto establish a connection to obtain a network resource.

Based on a same concept, FIG. 13 shows a terminal device 1300 accordingto an embodiment of this application. As shown in FIG. 13, some otherembodiments of this application include a terminal device 1300. Theterminal device 1300 may include one or more processors 1301, a memory1302, and one or more computer programs 1303. The foregoing componentsmay be connected by using one or more communications buses. The one ormore computer programs 1303 are stored in the memory 1302 and areconfigured to be executed by the one or more processors 1301. The one ormore computer programs 1303 include instructions, and the instructionsmay be used to enable the terminal device to perform the steps in FIG. 5to FIG. 9 and corresponding embodiments.

An embodiment of this application further provides a computer storagemedium. The storage medium may include a memory. The memory may store aprogram. When the program is executed, a terminal device is enabled toperform all the steps described in the method embodiments shown in FIG.5 or FIG. 9.

An embodiment of this application further provides a computer programproduct. When the computer program product is run on a terminal device,the terminal device is enabled to perform all the steps described in themethod embodiments shown in FIG. 5 to FIG. 9.

With descriptions of the foregoing implementations, a person skilled inthe art may clearly understand that the embodiments of this applicationmay be implemented by hardware, firmware, or a combination thereof. Whenthe embodiments of this application are implemented by software, theforegoing functions may be stored in a computer-readable medium ortransmitted as one or more instructions or code in the computer-readablemedium. The computer-readable medium includes a computer storage mediumand a communications medium, and the communications medium includes anymedium that enables a computer program to be transmitted from one placeto another. The storage medium may be any available medium accessible toa computer. This is used as an example but is not limited to: Thecomputer-readable medium may include a RAM, a ROM, an electricallyerasable programmable read-only memory (EEPROM), a compact discread-only memory (CD-ROM) or another compact disc storage, a magneticdisk storage medium or another magnetic storage device, or any othermedium that can be configured to carry or store desired program code ina form of an instruction or a data structure and that can be accessed bya computer. In addition, any connection may be appropriately defined asa computer-readable medium. For example, if software is transmitted froma website, a server, or another remote source by using a coaxial cable,an optical fiber/cable, a twisted pair, a digital subscriber line (DSL),or wireless technologies such as infrared ray, radio, and microwave, thecoaxial cable, optical fiber/cable, twisted pair, DSL, or wirelesstechnologies such as infrared ray, radio, and microwave are included infixation of a medium to which they belong. A disk and disc used in theembodiments of this application include a compact disc (CD), a laserdisc, an optical disc, a digital video disc (DVD), a floppy disk, and aBlu-ray disc. The disk usually magnetically copies data, and the discoptically copies data in a laser manner. The foregoing combinationshould also be included in the protection scope of the computer-readablemedium.

In conclusion, what is described above is merely the embodiments of thisapplication, but is not intended to limit the protection scope of thisapplication. Any modification, equivalent replacement, or improvementmade according to the disclosure of this application shall fall withinthe protection scope of this application.

1. A server node selection method, comprising: sending, by a terminaldevice, a domain name resolution request to a DNS server, wherein thedomain name resolution request carries a domain name, and the domainname resolution request requests an IP address corresponding to thedomain name; receiving, by the terminal device, a plurality of IPaddresses fed back by the DNS server in response to the domain nameresolution request, wherein each of the plurality of IP addressescorresponds to a server node in a plurality of server node; sending, bythe terminal device, a connection request to one server node in theplurality of server nodes at a first moment; determining whether theterminal device receives, before a second moment, response informationfed back by the one server node in response to the connection request;upon determination that the terminal device receives, before the secondmoment, the response information fed back by the one server node,establishing, by the terminal device, a connection to the one servernode; upon determination that the terminal device does not receive,before the second moment, the the response information fed back by theone server node, sending, by the terminal device, another connectionrequest to another server node in the plurality of server nodes at thesecond moment; receiving, by the terminal device, first responseinformation at a moment between the second moment and a third moment;and establishing, by the terminal device, a connection to a server nodethat sends the first response information, wherein the server node thatsends the first response information is the one server node or theanother server node.
 2. The method according to claim 1, furthercomprising: upon receiving second response information, discarding orskipping responding to, by the terminal device, the second responseinformation, wherein a server node that sends the second responseinformation is the one server node or the another server node, and isdifferent from the server node that sends the first responseinformation.
 3. The method according to claim 1, wherein the firstresponse information is sent by the one server node, before theestablishing, by the terminal device, the connection to the one servernode, and the method further comprises: waiting for, by the terminaldevice, a first preset duration starting from a fourth moment at whichthe terminal device receives the first response information, todetermine that the terminal device does not receive, within the firstpreset duration, response information sent by the another server node,wherein the first preset duration is shorter than an interval betweenthe fourth moment and the third moment.
 4. The method according to claim1, wherein an interval between the first moment and the second moment isthe same as an interval between the second moment and the third moment.5. The method according to claim 1, further comprising: sending, by theterminal device, a network resource request to the server node thatsends the first response information, wherein the network resourcerequest requests a network resource; and determining whether theterminal device does not receive, within a second preset duration, thenetwork resource fed back by the server node that sends the firstresponse information in response to the network resource request; upondetermination that the terminal device does not receive, within thesecond preset duration, the network resource fed back by the server nodethat sends the first response information, sending, by the terminaldevice, a network resource request to the server node that sends thesecond response information. 6-12. (canceled)
 13. A terminal device,comprising at least one processor and a memory, wherein the memory isconfigured to store one or more computer programs that, when executed bythe at least one processor, enable the terminal device to performoperations comprising: sending a domain name resolution request to a DNSserver, wherein the domain name resolution request carries a domainname, and the domain name resolution request requests an IP addresscorresponding to the domain name; receiving a plurality of IP addressesfed back by the DNS server in response to the domain name resolutionrequest, wherein each of the plurality of IP addresses corresponds to aserver node in a plurality of server node; sending a connection requestto one server node in the plurality of server nodes at a first moment;determining whether the terminal device receives, before a secondmoment, response information fed back by the one server node in responseto the connection request; upon determination that the terminal devicereceives, before the second moment, the response information fed back bythe one server node, establishing a connection to the one server node;upon determination that the terminal device does not receive, before thesecond moment, the response information fed back by the one server node,sending another connection request to another server node in theplurality of server nodes at the second moment; receiving first responseinformation at a moment between the second moment and a third moment;and establishing a connection to a server node that sends the firstresponse information, wherein the server node that sends the firstresponse information is the one server node or the another server node.14. The terminal device according to claim 13, wherein, when the one ormore computer programs stored in the memory are executed by the at leastone processor, the terminal device is further enabled to performoperations comprising: receiving second response information; anddiscarding or skipping responding to the second response information,wherein a server node that sends the second response information is theone server node or the another server node, and is different from theserver node that sends the first response information.
 15. The terminaldevice according to claim 13, wherein, when the one or more computerprograms stored in the memory are executed by the at least oneprocessor, the terminal device is further enabled to perform operationscomprising: determining that the first response information is sent bythe one server node; and waiting for a first preset duration startingfrom a fourth moment at which the terminal device receives the firstresponse information, to determine that the terminal device does notreceive, within the first preset duration, the second responseinformation sent by the another server node, wherein the first presetduration is shorter than an interval between the fourth moment and thethird moment.
 16. The terminal device according to claim 13, wherein aninterval between the first moment and the second moment is the same asan interval between the second moment and the third moment.
 17. Theterminal device according to claim 13, wherein, when the one or morecomputer programs stored in the memory are executed by the at least oneprocessor, the terminal device is further enabled to perform operationscomprising: sending a network resource request to the server node thatsends the first response information, wherein the network resourcerequest requests a network resource; determining whether the terminaldevice does not receive, within a second preset duration, the networkresource fed back by the server node that sends the first responseinformation in response to the network resource request; and upondetermination that the terminal device does not receive, within thesecond preset duration, the network resource fed back by the server nodethat sends the first response information in response to the networkresource request, sending a network resource request to the server nodethat sends the second response information. 18-24. (canceled)
 25. Acomputer storage medium, wherein the computer storage medium comprisesone or more computer programs that, when run on a terminal device,enable the terminal device perform operations comprising: sending adomain name resolution request to a DNS server, wherein the domain nameresolution request carries a domain name, and the domain name resolutionrequest requests an IP address corresponding to the domain name;receiving a plurality of IP addresses fed back by the DNS server inresponse to the domain name resolution request, wherein each of theplurality of IP addresses corresponds to a server node in a plurality ofserver nodes; sending a connection request to one server node in theplurality of server nodes at a first moment; determining whether theterminal device receives, before a second moment, response informationfed back by the one server node in response to the connection request;upon determination that the terminal device receives, before the secondmoment, the response information fed back by the one server node,establishing a connection to the one server node; upon determinationthat the terminal device does not receive, before the second moment, theresponse information fed back by the one server node, sending anotherconnection request to another server node in the plurality of servernodes at the second moment; receiving first response information at amoment between the second moment and a third moment, and establishing aconnection to a server node that sends the first response information,wherein the server node that sends the first response information is theone server node or the another server node.
 26. (canceled)
 27. Thecomputer storage medium according to claim 25, wherein, when the one ormore computer programs are run on the terminal device, the terminaldevice is further enabled to perform operations comprising: receivingsecond response information; and discarding or skipping responding tothe second response information, wherein a server node that sends thesecond response information is the one server node or the another servernode, and is different from the server node that sends the firstresponse information.
 28. The computer storage medium according to claim25, wherein, when the one or more computer programs are run on theterminal device, the terminal device is further enabled to performoperations comprising: determining that the first response informationis sent by the one server node; and waiting for a first preset durationstarting from a fourth moment at which the terminal device receives thefirst response information, to determine that the terminal device doesnot receive, within the first preset duration, response information sentby the another server node, wherein the first preset duration is shorterthan an interval between the fourth moment and the third moment.
 29. Theterminal device according to claim 13, wherein an interval between thefirst moment and the second moment is the same as an interval betweenthe second moment and the third moment.
 30. The terminal deviceaccording to claim 13, wherein, when the one or more computer programsstored in the memory are executed by the at least one processor, theterminal device is further enabled to perform the following operations:sending a network resource request to the server node that sends thefirst response information, wherein the network resource requestrequests a network resource; determining whether the terminal devicedoes not receive, within a second preset duration, the network resourcefed back by the server node that sends the first response information inresponse to the network resource request; and upon determination thatthe terminal device does not receive, within the second preset duration,the network resource fed back by the server node that sends the firstresponse information, sending a network resource request to the servernode that sends the second response information.